Systems and methods for dynamic prioritized transmission and receipt of data packets to and from a radio access network during an attach procedure

ABSTRACT

A user equipment (UE) may receive, during release from a radio access network (RAN), resource information associated with attaching to the RAN, wherein the resource information is received based on the device being authenticated. The UE may store the resource information in a data structure associated with the UE, and may receive, when the UE includes a payload of data packets to transmit to the RAN, a signal from the RAN. The UE may determine, based on the signal, whether the RAN is a same RAN that provided the resource information, and may determine whether a strength of the signal from the RAN satisfies a threshold when the RAN is the same RAN that provided the resource information. The UE may attach to the RAN when the strength of the signal satisfies the threshold, and may provide the payload to the RAN via a random access channel of the RAN.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/825,367, entitled “SYSTEMS AND METHODS FOR DYNAMIC PRIORITIZEDTRANSMISSION AND RECEIPT OF DATA PACKETS TO AND FROM A RADIO ACCESSNETWORK DURING AN ATTACH PROCEDURE,” filed Mar. 20, 2020, which isincorporated herein by reference in its entirety.

BACKGROUND

A user equipment (UE) may attempt to access a radio access network (RAN)using a random access channel (RACH) attach procedure. The attachprocedure allows the UE to establish a connection with a RAN device(e.g., a gNodeB, a base station, an eNodeB, and/or the like) that servesthe UE.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1E are diagrams of one or more example implementationsdescribed herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2 .

FIG. 4 is a flow chart of an example process for providing dynamicprioritized transmission and/or receipt of data packets to and/or from aRAN during an attach procedure.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A current attach procedure for a UE with a RAN begins with a randomaccess attempt of the RAN by the UE. If the random access attempt issuccessful, the UE may be configured for resources used at attach inorder to transmit and/or receive data packets (user applicationpackets). Unfortunately, the current attach procedure adds latency to UEaccess of the RAN, which prevents the UE from transmitting and/orreceiving data packets. Another procedure is provided to release the UEfrom the RAN whenever the UE enters into an idle state. When thereleased UE has data packets to transmit and/or receive, the UEreattaches to the RAN using the current attach procedure and the randomaccess attempt. In RANs, such as fourth generation (4G) and fifthgeneration (5G) RANs, the current attach procedure is reserved fortransmission of over-the-air (OTA) signaling-related data. Thus, thecurrent attach procedure inefficiently utilizes and wastes computingresources (e.g., processing resources, memory resources, communicationresources, and/or the like), networking resources, and/or the likeassociated with preventing data packets from being transmitted and/orreceived during an attach with the RAN, causing delays in transmissionand/or reception of the data packets, and/or the like.

Some implementations described herein provide a UE that provides dynamicprioritized transmission and/or receipt of data packets to and/or from aRAN during an attach procedure. For example, the UE may receive, duringrelease from the RAN, resource information associated with attaching tothe RAN, wherein the resource information is received based on the UEbeing authenticated for transmitting and receiving data packets during are-attach with the RAN. The UE may receive information that would maketransmission at an initial stage (e.g., before dedicated signaling) toimprove latency. For example, the UE may need to encrypt data fortransmission, and an encryption configuration may be provided to the UEat release so that the encryption configuration may be used in fastreattach. A new encryption may be established once the UE attaches againto the RAN. To minimize contention during re-attach, the RAN may alsoprovide, to the UE, resource information (e.g., which frequency and/ortime slots to use) the UE is to utilize when the attempting to attachagain to the same RAN. The UE may store the resource information in adata structure associated with the UE, and may receive, when the UEincludes a payload of data packets to transmit to the RAN, a signal fromthe RAN. The UE may determine, based on the signal, whether the RAN isthe same RAN that provided the resource information, and maysubsequently determine whether a strength of the signal from the RANsatisfies a threshold. The UE may attach to the RAN when the strength ofthe signal satisfies the threshold, and may provide the payload to theRAN via a random access channel of the RAN.

In this way, the UE provides dynamic prioritized transmission and/orreceipt of data packets to and/or from a RAN during a random accessattach procedure. Based on the UE being authenticated and during releaseby the RAN, the UE may be provisioned (e.g., by the RAN) with resourceinformation related to a next attach by the UE with the RAN. Theresource information may be utilized by the UE to transmit and/orreceive (e.g., in certain radio frequency (RF) conditions) data packetsduring a random access attempt. This would reduce latency and improvecapacity for the UE by allowing the UE to transmit and/or receive datapackets over more channels and at an earlier stage. Thus, the UEconserves computing resources, networking resources, and/or the likethat would otherwise be inefficiently utilized and wasted in preventingdata packets from being transmitted and/or received during an attachwith the RAN, causing delays in transmission and/or reception of thedata packets, and/or the like.

FIGS. 1A-1E are diagrams of one or more example implementations 100described herein. As shown in FIG. 1A, a user equipment (UE) 105 may beassociated with a radio access network (RAN) 110 and a core network 115.UE 105 may include a mobile phone, a laptop computer, a tablet computer,and/or the like that attaches to RAN 110. RAN 110 may include one ormore network devices (e.g., eNodeBs, gNodeBs, and/or the like) thatprovide UE 105 with access to core network 115. Core network 115 mayinclude an example architecture of a 4G core network, a 5G core networkincluded in a 5G wireless telecommunications system, and/or the like.

As further shown in FIG. 1A, and by reference number 120, RAN 110 maydetermine that a UE activity timer has expired. For example, the UEactivity timer may expire due to inactivity associated with UE 105(e.g., measured in seconds, minutes, and/or the like). The UE activitytimer may also be referred to as a UE inactivity timer. When RAN 110detects that UE 105 does not have traffic to send and/or receive duringa defined period of time (e.g., defined by the UE activity timer), RAN110 may initiate procedures to place UE 105 in an idle mode. The UEactivity timer may be defined in RAN 110 and may be configurable.

As further shown in FIG. 1A, and by reference number 125, RAN 110 maydetermine whether UE 105 is authenticated for fast access during are-attach. For example, a base station of RAN 110 may determine whetherUE 105 supports a fast access procedure. In some aspects, a fast accessprocedure is one in which UE 105 will not have to be configured forresources at re-attach in order to transmit and/or receive data packetsto and/or from RAN 110. RAN 110 may determine whether UE 105 may benefitfrom a fast access procedure in relation to applications used and/or aradio frequency (RF) condition at the time of release of UE 105, and maydetermine that UE 105 is authenticated for fast access during are-attach only when UE 105 may benefit from a fast access procedure inrelation to the applications used and/or the RF condition at the time ofrelease of UE 105. For example, RAN 110 may determine that any dataapplication type utilizes a small data payload (e.g., latency-sensitiveapplications, delay-sensitive applications, applications with smallpayloads, and/or the like) is eligible for the fast access procedure(e.g., a web request type where a session usually begins with a requestbefore larger content is transmitted and/or received).

For example, UE 105 may benefit from the fast access procedure when UE105 is released from RAN 110 and has data packets to transmit to and/orreceive from RAN 110. UE 105 may utilize fast access procedure whenreattaching to RAN 110 to transmit the data packets to or receive thedata packets from RAN 110 during the attach procedure with RAN 110. Thisprevents delays in transmission and/or reception of the data packets,which may improve a user experience for a user of UE 105.

As further shown in FIG. 1A, and by reference number 130, RAN 110 mayrelease UE 105 with resource information associated with attaching toRAN 110 based on UE 105 being authenticated for the fast access during are-attach. The resource information may be based on Internet protocol(IP) and encryption configurations associated with data packetstransmitted to and/or received by UE 105. Additionally, oralternatively, the resource information may include resource blocks tobe allocated to UE 105 during a re-attach with RAN 110. The resourceinformation may include additional data related to a resourceinformation configuration to be used when UE 105 is released (e.g., asignature provided to UE 105 that indicates that UE 105 has been vettedand is authenticated). Additionally, or alternatively, the resourceinformation may include a physical cell identity (PCI) list associatedwith base stations of RAN 110 that are able to forward data packets viaan IP tunnel.

As further shown in FIG. 1A, and by reference number 135, UE 105 mayreceive and store the resource information. UE 105 may periodicallyreceive the resource information, may receive the resource informationbased on a request, and/or the like. UE 105 may store the resourceinformation in a data structure (e.g., a database, a table, a list,and/or the like) associated with UE 105. In some implementations, UE 105receives information identifying a quantity of resource blocks to beallocated to UE 105 during a re-attach with RAN 110. In this case, theinformation identifying the quantity of resource blocks may correspondto the resource information, and the quantity of resource blocks may bedependent on quantities of resource blocks allocated to other UEs 105associated with RAN 110. In this way, UE 105 may be configured atconnection release with the resource information necessary to reattachin the future, and may receive and store the resource information foruse in a future reattach procedure. Furthermore, by receiving andstoring resource blocks to be allocated to UE 105 during a re-attachwith RAN 110, and by receiving and storing information identifying aquantity of resource blocks to be allocated to UE 105 during re-attachwith RAN 110, UE 105 may enable RAN 110 to more evenly distributeresources across UEs 105 that connect to RAN 110, which may allow forless contention at a next attempt to re-attach with RAN 110.

As shown in FIG. 1B, and by reference number 140, UE 105 may receive asignal from RAN 110. The signal may include a radio frequency (RF)signal generated by RAN 110. At the time the signal is received, UE 105may be in an idle state, and may include a payload for an uplinktransmission to RAN 110. In some implementations, UE 105 mayperiodically monitor the signal associated with RAN 110, and maydetermine a RAN measurement. For example, the RAN measurement mayinclude a signal-to-noise ratio (SNR), a reference signal received power(RSRP), key performance indicators (KPIs), and/or the like for thesignal.

As further shown in FIG. 1B, and by reference number 145, UE 105 maydetermine, based on the signal, whether RAN 110 is the same RAN 110 towhich UE 105 was previously attached. For example, UE 105 may determinewhether a base station of RAN 110, to which UE 105 is attempting toattach, is a same base station from which UE 105 was previouslyreleased. Additionally, or alternatively, UE 105 may determine, based onthe signal, whether the base station is identified in a physical cellidentity (PCI) list associated with base stations that are able toforward data packets on an IP tunnel.

As shown in FIG. 1C, and by reference number 150, UE 105 may determinewhether a strength of the signal from RAN 110 satisfies a threshold whenRAN 110 is the same RAN to which UE 105 was previously attached. Forexample, UE 105 may determine whether the RAN measurement (e.g., theSNR, the RSRP, the KPIs, and/or the like) satisfies a signal strengththreshold. When the RAN measurement is an RSRP measurement of a 5Gsignal, UE 105 may determine whether the RAN measurement satisfies a 5Gthreshold, such as an evolved-UMTS terrestrial radio access network(E-UTRAN) new radio-dual connectivity (EN-DC) add threshold, a newradio-dual connectivity (NR-DC) add threshold, a new radio-carrieraggregation (NR-CA) add threshold, and/or the like. By determiningwhether the strength of the signal from RAN 110 satisfies the threshold,UE 105 may determine whether the signal includes an RF condition that issufficient to transmit a data payload in an uplink transmission.

As further shown in FIG. 1C, and by reference number 155, UE 105 mayattach to RAN 110 and provide the uplink transmission of the payload viaa random access channel of RAN 110 when the strength of the signalsatisfies the threshold. For example, when UE 105 determines that thestrength of the signal from RAN 110 satisfies the threshold, UE 105 maytransmit the payload to RAN 110 via the random access channel of RAN 110and without performing an authentication process with RAN 110.

In this way, by providing the payload to RAN 110 via the random accesschannel of RAN 110, UE 105 may reduce latency for UE 105 relative to notproviding the payload to RAN 110 via the random access channel. In someimplementations, UE 105 provides, to RAN 110, signaling data with thepayload via the random access channel of RAN 110. In someimplementations, UE 105 prevents provision of the payload to RAN 110,via the random access channel of RAN 110, when RAN 110 is not the sameRAN that provided the resource information. In some implementations, UE105 prevents provision of the payload to RAN 110, via the random accesschannel of RAN 110, when the strength of the signal fails to satisfy thethreshold. In such situations, UE 105 may utilize the regular attachprocedure to attach to RAN 110, and may provide the payload to RAN 110once attached to RAN 110 via the regular attach procedure.

As shown in FIG. 1D, and by reference number 160, UE 105 may receive asignal from RAN 110. At the time the signal is received, UE 105 may havepreviously detached from RAN 110 and may be in an idle state. RAN 110may include a payload for a downlink transmission to UE 105. Forexample, RAN 110 may include the payload for transmission to UE 105, andthe signal may indicate that the payload is pending in RAN 110 fortransmission to UE 105.

As further shown in FIG. 1D, and by reference number 165, UE 105 maydetermine, based on the signal, whether RAN 110 is the same RAN to whichUE 105 was previously attached. For example, UE 105 may determinewhether a base station of RAN 110, to which UE 105 is attempting toattach, is a same base station from which UE 105 was previouslyreleased. In some implementations, UE 105 may periodically monitor thesignal associated with RAN 110, and may determine a RAN measurement(e.g., an SNR, an RSRP, KPIs, and/or the like) for the signal, asdescribed above in connection with FIG. 1B.

As shown in FIG. 1E, and by reference number 170, UE 105 may determinewhether a strength of the signal from RAN 110 satisfies a threshold whenRAN 110 is the same RAN to which UE 105 was previously attached. Forexample, UE 105 may determine whether the RAN measurement (e.g., theSNR, the RSRP, the KPIs, and/or the like) satisfies a signal strengththreshold. When the RAN measurement is an RSRP measurement of a 5Gsignal, UE 105 may determine whether the RAN measurement satisfies a 5Gthreshold, such as an EN-DC add threshold, an NR-DC add threshold, anNR-CA add threshold, and/or the like, as described above in connectionwith FIG. 1B. By determining whether the strength of the signal from RAN110 satisfies the threshold, UE 105 may determine whether the signalincludes an RF condition that is sufficient to receive a data payload ina downlink transmission.

As further shown in FIG. 1E, and by reference number 175, UE 105 mayattach to RAN 110 and may receive the downlink transmission of thepayload via a random access channel of RAN 110 when the strength of thesignal satisfies the threshold. For example, a base station of RAN 110may attempt to send data packets along with connection attachinformation in a contention resolution message in an attach procedure,such as an MSG-4 message in a four message contention-based randomaccess channel handshake procedure (e.g., managed by a radio networkcontroller of RAN 110). The procedure may include a physical randomaccess channel preamble (MSG-1) in which UE 105 randomly selects andtransmits a preamble code to the base station of RAN 110 on the physicalrandom access channel, and a random access response (MSG-2). The randomaccess response may include detection of access requests sent by UEs 105to RAN 110, assignment of a temporary cell radio network temporaryidentifier (TC-RNTI) to UEs 105, a resource grant in an uplink channelfor subsequent message exchanges between UEs 105 and RAN 110, and/or thelike. The procedure may also include a connection request (MSG-3) inwhich UE 105 sends the TC-RNTI assigned in MSG-2 over an uplink sharedchannel, and a connection request (MSG-4) that is a contentionresolution message that UE 105 waits for the base station to send in adownlink shared channel. In this case, if a device identifier is presentin the contention resolution message, UE 105 may send an acknowledgment(ACK) message to the base station, and if a device identifier is notpresent in the contention message, UE 105 may randomly select a back-offtime before retrying transmission.

UE 105 may thereafter receive the downlink payload from RAN 110 via therandom access channel of RAN 110. UE 105 may receive, from RAN 110,signaling data with the downlink payload via the random access channelof RAN 110. UE 105 may prevent reception of the downlink payload fromRAN 110, via the random access channel of RAN 110, when RAN 110 is notthe same RAN that provided the resource information. UE 105 may alsoprevent reception of the downlink payload from RAN 110, via the randomaccess channel of RAN 110, when the strength of the signal fails tosatisfy the threshold. In such situations, UE 105 may utilize theregular attach procedure to attach to RAN 110, and UE 105 may receivethe payload from RAN 110 once attached to RAN 110 via the regular attachprocedure.

In this way, UE 105 provides dynamic prioritized transmission and/orreceipt of data packets to and/or from RAN 110 during an attachprocedure. For example, UE 105 may prioritize particular applications ortypes of data in terms of how fast to transmit and/or receive data fromRAN 110. The prioritized transmission and/or receipt of data may bebased on radio frequency and payload data type to allow UE 105 totransmit and/or receive data faster over RAN 110. In another example,based on UE 105 being authenticated and during release by RAN 105, UE105 may be provisioned (e.g., by RAN 110) with resource informationrelated to a next attach by UE 105 with RAN 110. The resourceinformation may be utilized by UE 105 to transmit (e.g., an uplinkpayload) and/or receive (e.g., a downlink payload received from RAN 110)data packets during a random access attempt with RAN 110. This wouldreduce latency and improve capacity for UE 105 by allowing UE 105 totransmit and/or receive data packets to and/or from RAN 110 over morechannels and at an earlier stage. Thus, UE 105 conserves computingresources, networking resources, and/or the like that would otherwise beinefficiently utilized and wasted in preventing data packets from beingtransmitted and/or received during an attach with the RAN, causingdelays in transmission and/or reception of the data packets, and/or thelike.

As indicated above, FIGS. 1A-1E are provided merely as examples. Otherexamples may differ from what is described with regard to FIGS. 1A-1E.The number and arrangement of devices and networks shown in FIGS. 1A-1Eare provided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIGS. 1A-1E. Furthermore, two or more devices shown in FIGS.1A-1E may be implemented within a single device, or a single deviceshown in FIGS. 1A-1E may be implemented as multiple, distributeddevices. Additionally, or alternatively, a set of devices (e.g., one ormore devices) of FIGS. 1A-1E may perform one or more functions describedas being performed by another set of devices of FIGS. 1A-1E.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. As shown in FIG. 2 ,example environment 200 may include UE 105, RAN 110, core network 115,and a data network 255. Devices and/or networks of example environment200 may interconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

UE 105 includes one or more devices capable of receiving, generating,storing, processing, and/or providing information, such as informationdescribed herein. For example, UE 105 can include a mobile phone (e.g.,a smart phone, a radiotelephone, and/or the like), a laptop computer, atablet computer, a desktop computer, a handheld computer, a gamingdevice, a wearable communication device (e.g., a smart watch, a pair ofsmart glasses, and/or the like), a mobile hotspot device, a fixedwireless access device, customer premises equipment, an autonomousvehicle, or a similar type of device.

RAN 110 may support, for example, a cellular radio access technology(RAT). RAN 110 may include one or more base stations (e.g., basetransceiver stations, radio base stations, node Bs, eNodeBs (eNBs),gNodeBs (gNBs), base station subsystems, cellular sites, cellulartowers, access points, transmit receive points (TRPs), radio accessnodes, macrocell base stations, microcell base stations, picocell basestations, femtocell base stations, or similar types of devices) andother network entities that can support wireless communication for UE105. RAN 110 may transfer traffic between UE 105 (e.g., using a cellularRAT), one or more base stations (e.g., using a wireless interface or abackhaul interface, such as a wired backhaul interface), and/or corenetwork 115. RAN 110 may provide one or more cells that cover geographicareas.

In some implementations, RAN 110 may perform scheduling and/or resourcemanagement for UE 105 covered by RAN 110 (e.g., UE 105 covered by a cellprovided by RAN 110). In some implementations, RAN 110 may be controlledor coordinated by a network controller, which may perform loadbalancing, network-level configuration, and/or the like. The networkcontroller may communicate with RAN 110 via a wireless or wirelinebackhaul. In some implementations, RAN 110 may include a networkcontroller, a self-organizing network (SON) module or component, or asimilar module or component. In other words, RAN 110 may perform networkcontrol, scheduling, and/or network management functions (e.g., foruplink, downlink, and/or sidelink communications of UE 105 covered byRAN 110).

In some implementations, core network 115 may include an examplefunctional architecture in which systems and/or methods described hereinmay be implemented. For example, core network 115 may include an examplearchitecture of a fifth generation (5G) next generation (NG) corenetwork included in a 5G wireless telecommunications system. While theexample architecture of core network 115 shown in FIG. 2 may be anexample of a service-based architecture, in some implementations, corenetwork 115 may be implemented as a reference-point architecture, a 4Gcore network, and/or the like.

As shown in FIG. 2 , core network 115 may include a number of functionalelements. The functional elements may include, for example, a networkslice selection function (NSSF) 205, a network exposure function (NEF)210, an authentication server function (AUSF) 215, a unified datamanagement (UDM) component 220, a policy control function (PCF) 225, anapplication function (AF) 230, an access and mobility managementfunction (AMF) 235, a session management function (SMF) 240, a userplane function (UPF) 245, and/or the like. These functional elements maybe communicatively connected via a message bus 250. Each of thefunctional elements shown in FIG. 2 is implemented on one or moredevices associated with a wireless telecommunications system. In someimplementations, one or more of the functional elements may beimplemented on physical devices, such as an access point, a basestation, a gateway, and/or the like. In some implementations, one ormore of the functional elements may be implemented on a computing deviceof a cloud computing environment.

NSSF 205 includes one or more devices that select network sliceinstances for UE 105. By providing network slicing, NSSF 205 allows anoperator to deploy multiple substantially independent end-to-endnetworks potentially with the same infrastructure. In someimplementations, each slice may be customized for different services.

NEF 210 includes one or more devices that support exposure ofcapabilities and/or events in the wireless telecommunications system tohelp other entities in the wireless telecommunications system discovernetwork services.

AUSF 215 includes one or more devices that act as an authenticationserver and support the process of authenticating UE 105 in the wirelesstelecommunications system.

UDM 220 includes one or more devices that store user data and profilesin the wireless telecommunications system. UDM 220 may be used for fixedaccess, mobile access, and/or the like, in core network 115.

PCF 225 includes one or more devices that provide a policy frameworkthat incorporates network slicing, roaming, packet processing, mobilitymanagement, and/or the like.

AF 230 includes one or more devices that support application influenceon traffic routing, access to NEF 210, policy control, and/or the like.

AMF 235 includes one or more devices that act as a termination point fornon-access stratum (NAS) signaling, mobility management, and/or thelike.

SMF 240 includes one or more devices that support the establishment,modification, and release of communication sessions in the wirelesstelecommunications system. For example, SMF 240 may configure trafficsteering policies at UPF 245, enforce user equipment IP addressallocation and policies, and/or the like.

UPF 245 includes one or more devices that serve as an anchor point forintraRAT and/or interRAT mobility. UPF 245 may apply rules to packets,such as rules pertaining to packet routing, traffic reporting, handlinguser plane QoS, and/or the like.

Message bus 250 represents a communication structure for communicationamong the functional elements. In other words, message bus 250 maypermit communication between two or more functional elements.

Data network 255 includes one or more wired and/or wireless datanetworks. For example, data network 255 may include an IP MultimediaSubsystem (IMS), a public land mobile network (PLMN), a local areanetwork (LAN), a wide area network (WAN), a metropolitan area network(MAN), a private network such as a corporate intranet, an ad hocnetwork, the Internet, a fiber optic-based network, a cloud computingnetwork, a third party services network, an operator services network,and/or the like, and/or a combination of these or other types ofnetworks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2 . Furthermore, two or more devices shown in FIG. 2 maybe implemented within a single device, or a single device shown in FIG.2 may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) of exampleenvironment 200 may perform one or more functions described as beingperformed by another set of devices of example environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to UE 105, a base station of RAN 110, NSSF 205, NEF 210,AUSF 215, UDM 220, PCF 225, AF 230, AMF 235, SMF 240, and/or UPF 245. Insome implementations, UE 105, the base station of RAN 110, NSSF 205, NEF210, AUSF 215, UDM 220, PCF 225, AF 230, AMF 235, SMF 240, and/or UPF245 may include one or more devices 300 and/or one or more components ofdevice 300. As shown in FIG. 3 , device 300 may include a bus 310, aprocessor 320, a memory 330, a storage component 340, an input component350, an output component 360, and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random-access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid-state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface,and/or the like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3 . Additionally, or alternatively,a set of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for providing dynamicprioritized transmission and/or receipt of data packets to and/or from aRAN during an attach procedure. In some implementations, one or moreprocess blocks of FIG. 4 may be performed by a device (e.g., UE 105). Insome implementations, one or more process blocks of FIG. 4 may beperformed by another device or a group of devices separate from orincluding the device, such as a RAN (e.g., RAN 110).

As shown in FIG. 4 , process 400 may include receiving, during releasefrom a radio access network, resource information associated withattaching to the radio access network, wherein the resource informationis received based on the device being authenticated for transmitting andreceiving data packets during a re-attach with the radio access network(block 410). For example, the device (e.g., using processor 320,communication interface 370, and/or the like) may receive, duringrelease from a radio access network, resource information associatedwith attaching to the radio access network, as described above. In someimplementations, the resource information may be received based on thedevice being authenticated for transmitting and receiving data packetsduring a re-attach with the radio access network. In someimplementations, the device may include a user equipment, and the radioaccess network may include one of a base transceiver station, a radiobase station, an eNodeB, or a gNodeB. In some implementations, theresource information may be based on Internet protocol and encryptionconfigurations associated with data packets transmitted and received bythe device. In some implementations, the resource information mayinclude resource blocks to be allocated to the device during a re-attachwith the radio access network.

As further shown in FIG. 4 , process 400 may include storing theresource information in a data structure associated with the device(block 420). For example, the device (e.g., using processor 320, memory330, and/or the like) may store the resource information in a datastructure associated with the device, as described above.

As further shown in FIG. 4 , process 400 may include receiving, when thedevice includes a payload of data packets to transmit to the radioaccess network, a signal from the radio access network (block 430). Forexample, the device (e.g., using processor 320, communication interface370, and/or the like) may receive, when the device includes a payload ofdata packets to transmit to the radio access network, a signal from theradio access network, as described above.

As further shown in FIG. 4 , process 400 may include determining, basedon the signal, whether the radio access network is a same radio accessnetwork that provided the resource information (block 440). For example,the device (e.g., using processor 320, storage component 340, and/or thelike) may determine, based on the signal, whether the radio accessnetwork is a same radio access network that provided the resourceinformation, as described above.

As further shown in FIG. 4 , process 400 may include determining whethera strength of the signal from the radio access network satisfies athreshold when the radio access network is the same radio access networkthat provided the resource information (block 450). For example, thedevice (e.g., using processor 320, memory 330, and/or the like) maydetermine whether a strength of the signal from the radio access networksatisfies a threshold when the radio access network is the same radioaccess network that provided the resource information, as describedabove.

As further shown in FIG. 4 , process 400 may include attaching to theradio access network when the strength of the signal satisfies thethreshold (block 460). For example, the device (e.g., using processor320, storage component 340, communication interface 370, and/or thelike) may attach to the radio access network when the strength of thesignal satisfies the threshold, as described above.

As further shown in FIG. 4 , process 400 may include providing thepayload to the radio access network via a random access channel of theradio access network (block 470). For example, the device (e.g., usingprocessor 320, memory 330, storage component 340, communicationinterface 370, and/or the like) may provide the payload to the radioaccess network via a random access channel of the radio access network,as described above. In some implementations, providing the payload tothe radio access network via the random access channel of the radioaccess network may reduce latency for the device relative to notproviding the payload to the radio access network via the random accesschannel.

Process 400 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, process 400 may include detaching the devicefrom the radio access network; receiving, when the radio access networkincludes another payload of data packets to transmit to the device,another signal from the radio access network; determining, based on theother signal, whether the radio access network is the same radio accessnetwork that provided the resource information; determining whether astrength of the other signal from the radio access network satisfies athreshold when the radio access network is the same radio access networkthat provided the resource information; attaching the device to theradio access network when the strength of the other signal satisfies thethreshold; and receiving the other payload from the radio access networkvia the random access channel of the radio access network.

In some implementations, process 400 may include receiving, from theradio access network, signaling data with the other payload via therandom access channel of the radio access network.

In some implementations, process 400 may include preventing the devicefrom receiving the other payload from the radio access network, via therandom access channel of the radio access network, when the radio accessnetwork is not the same radio access network that provided the resourceinformation.

In some implementations, process 400 may include preventing the devicefrom receiving the other payload from the radio access network, via therandom access channel of the radio access network, when the strength ofthe other signal fails to satisfy the threshold.

In some implementations, process 400 may include providing, to the radioaccess network, signaling data with the payload via the random accesschannel of the radio access network.

In some implementations, process 400 may include receiving informationidentifying a quantity of resource blocks to be allocated to the deviceduring a re-attach with the radio access network, wherein theinformation identifying the quantity of resource blocks may correspondto the resource information, and wherein the quantity of resource blocksmay be dependent on quantities of resource blocks allocated to otherdevices associated with the radio access network.

In some implementations, process 400 may include preventing the devicefrom providing the payload to the radio access network, via the randomaccess channel of the radio access network, when the radio accessnetwork is not the same radio access network that provided the resourceinformation.

In some implementations, process 400 may include preventing the devicefrom providing the payload to the radio access network, via the randomaccess channel of the radio access network, when the strength of thesignal fails to satisfy the threshold.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4 . Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations may be made inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, it should be understood thatsuch information shall be used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods described herein may beimplemented in different forms of hardware, firmware, or a combinationof hardware and software. The actual specialized control hardware orsoftware code used to implement these systems and/or methods is notlimiting of the implementations. Thus, the operation and behavior of thesystems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwaremay be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, and/or the like), and may be used interchangeably with“one or more.” Where only one item is intended, the phrase “only one” orsimilar language is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, by a device andduring release from a network, information associated with attaching tothe network, wherein the information is received based on the devicebeing authenticated; determining, by the device and based on a signalfrom the network, whether the network is a same network that providedthe information; determining, by the device and based on determiningthat the network is the same network that provided the information,whether a strength of the signal satisfies a threshold; attaching, bythe device and based on the strength of the signal satisfying thethreshold, to the network; and providing, by the device and based onattaching, data to the network.
 2. The method of claim 1, wherein theinformation is received based on re-attaching to the network.
 3. Themethod of claim 1, wherein the device is in an idle state beforereceiving the signal from the network, and wherein the device includesthe data for transmission to the network before receiving the signalfrom the network.
 4. The method of claim 1, wherein the network is aradio access network, and wherein the data is provided to the networkvia a random access channel of the network.
 5. The method of claim 1,wherein the data is first data, the signal is a first signal, and thethreshold is a first threshold, and wherein the method furthercomprises: receiving a second signal, wherein the second signalindicates that second data is pending in the network for transmission tothe device; and receiving, based on a strength of the second signalsatisfying a second threshold, the second data from the network.
 6. Themethod of claim 5, wherein the device is in an idle state beforereceiving at least one of: the first signal, or the second signal. 7.The method of claim 1, further comprising: preventing, based ondetermining that the network is not the same network that provided theinformation, the device from receiving other data from the network.
 8. Adevice, comprising: one or more processors configured to: receive,during release from a network, information associated with attaching tothe network, wherein the information is received based on the devicebeing authenticated; determine, based on a signal from the network,whether the network is a same network that provided the information;determine, based on determining that the network is the same networkthat provided the information, whether a strength of the signalsatisfies a threshold; attach, based on the strength of the signalsatisfying the threshold, to the network; and provide, based onattaching, data to the network.
 9. The device of claim 8, wherein theinformation is received based on re-attaching to the network.
 10. Thedevice of claim 8, wherein the device is in an idle state beforereceiving the signal from the network, and wherein the device includesthe data for transmission to the network before receiving the signalfrom the network.
 11. The device of claim 8, wherein the network is aradio access network, and wherein the data is provided to the networkvia a random access channel of the network.
 12. The device of claim 8,wherein the data is first data, the signal is a first signal, and thethreshold is a first threshold, and wherein the one or more processorsare further configured to: receive a second signal, wherein the secondsignal indicates that second data is pending in the network fortransmission to the device; and receive, based on a strength of thesecond signal satisfying a second threshold, the second data from thenetwork.
 13. The device of claim 12, wherein the device is in an idlestate before receiving at least one of: the first signal, or the secondsignal.
 14. The device of claim 8, wherein the one or more processorsare further configured to: prevent, based on determining that thenetwork is not the same network that provided the information, thedevice from receiving other data from the network.
 15. A non-transitorycomputer-readable medium storing a set of instructions, the set ofinstructions comprising: one or more instructions that, when executed byone or more processors of a device, cause the device to: receive, duringrelease from a network, information associated with attaching to thenetwork, wherein the information is received based on the device beingauthenticated; determine, based on a signal from the network, whetherthe network is a same network that provided the information; determine,based on determining that the network is the same network that providedthe information, whether a strength of the signal satisfies a threshold;attach, based on the strength of the signal satisfying the threshold, tothe network; and provide, based on attaching, data to the network. 16.The non-transitory computer-readable medium of claim 15, wherein theinformation is received based on re-attaching to the network.
 17. Thenon-transitory computer-readable medium of claim 15, wherein the deviceis in an idle state before receiving the signal from the network, andwherein the device includes the data for transmission to the networkbefore receiving the signal from the network.
 18. The non-transitorycomputer-readable medium of claim 15, wherein the network is a radioaccess network, and wherein the data is provided to the network via arandom access channel of the network.
 19. The non-transitorycomputer-readable medium of claim 15, wherein the data is first data,the signal is a first signal, and the threshold is a first threshold,and wherein the one or more instructions further cause the device to:receive a second signal, wherein the second signal indicates that seconddata is pending in the network for transmission to the device; andreceive, based on a strength of the second signal satisfying a secondthreshold, the second data from the network.
 20. The non-transitorycomputer-readable medium of claim 15, wherein the one or moreinstructions further cause the device to: prevent, based on determiningthat the network is not the same network that provided the information,the device from receiving other data from the network.